Personalized wait treatment during interaction

ABSTRACT

A communication session with a communication endpoint is established. The communication session is placed on hold. For example, the communication session is placed on hold by being sent to a contact center queue. In response to placing the communication session on hold, a message is sent to the communication endpoint that indicates the communication session has been placed on hold. In response to the message, the communication endpoint may initiate a second media stream, such as to play personal media while the communication session is on hold. The second media stream may be a local media file or a remote media file, such as an internet radio station. In response to determining that the communication session is taken off hold, a second message is sent to the communication endpoint to stop playing the personalized media. This process allows the user to play personalized media while being placed on hold.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 16/732,734, filed on Jan. 2, 2020, which is a continuation of and claims priority to U.S. patent application Ser. No. 15/938,283, filed on Mar. 28, 2018. Each of the aforementioned documents is incorporated herein by this reference in their entirety for all that they teach and for all purposes.

FIELD

The disclosure relates generally to managing how calls are placed on hold.

BACKGROUND

Traditionally, customers would call into a contact center using telephone equipment. For example, a customer may call into the contact center using a landline telephone or mobile telephone. The customer would then be placed on hold while waiting to be serviced by the contact center. While on hold, the customer may hear music or a feed of a radio station that is provided by the contact center.

Today, customers have shifted towards more of a “Web” centric or application centric solution to connect to the contact center. With the advent of technology, such as, Web Real-Time Communication (WebRTC), the customers of today prefer to make audio/video calls through an application running inside a web browser or a downloaded application. In this new paradigm, the problem of a customer having to wait to be serviced by a contact center agent still exists. If the call volume is high, the customer has to listen to generic music played by a contact center Interactive Voice Response (IVR) system or similar. At times, this can be quite irritating for the customer since not only does the customer have to wait for an extended period, but the customer has no option other than to listen to the generic music played by the contact center IVR system.

SUMMARY

These and other needs are addressed by the various embodiments and configurations of the present disclosure. A communication session with a communication endpoint is established. The communication session is placed on hold. For example, the communication session is placed on hold by being sent to a contact center queue. In response to placing the communication session on hold, a first message is sent to the communication endpoint that indicates the communication session has been placed on hold. A second message is received from the communication endpoint that indicates that a user of the communication endpoint would like to play personal media while the communication session is on hold. The communication session is later taken off hold. In response to determining that the communication session is taken off hold, a third message is sent to the communication endpoint to stop playing the personalized media. This process allows the user to play personalized media while being placed on hold.

The phrases “at least one”, “one or more”, “or”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C”, “A, B, and/or C”, and “A, B, or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers to any process or operation, which is typically continuous or semi-continuous, done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be “material”.

Aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium.

A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The terms “determine”, “calculate” and “compute,” and variations thereof, as used herein, are used interchangeably and include any type of methodology, process, mathematical operation or technique.

The term “Session Initiation Protocol” (SIP) as used herein refers to an IETF-defined signaling protocol, widely used for controlling multimedia communication sessions such as voice and video calls over Internet Protocol (IP). The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty (multicast) sessions consisting of one or several media streams. The modification can involve changing addresses or ports, inviting more participants, and adding or deleting media streams. Other feasible application examples include video conferencing, streaming multimedia distribution, instant messaging, presence information, file transfer and online games. SIP is as described in RFC 3261, available from the Internet Engineering Task Force (IETF) Network Working Group, November 2000; this document and all other SIP RFCs describing SIP are hereby incorporated by reference in their entirety for all that they teach.

The term “means” as used herein shall be given its broadest possible interpretation in accordance with 35 U.S.C., Section 112(f) and/or Section 112, Paragraph 6. Accordingly, a claim incorporating the term “means” shall cover all structures, materials, or acts set forth herein, and all of the equivalents thereof. Further, the structures, materials or acts and the equivalents thereof shall include all those described in the summary, brief description of the drawings, detailed description, abstract, and claims themselves.

The preceding is a simplified summary to provide an understanding of some aspects of the disclosure. This summary is neither an extensive nor exhaustive overview of the disclosure and its various embodiments. It is intended neither to identify key or critical elements of the disclosure nor to delineate the scope of the disclosure but to present selected concepts of the disclosure in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the disclosure are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below. Also, while the disclosure is presented in terms of exemplary embodiments, it should be appreciated that individual aspects of the disclosure can be separately claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a first illustrative system for playing personal media while on a user is placed on hold by a contact center.

FIG. 2 is a diagram of a user interface for selecting personal media while a user is placed on hold by a contact center.

FIG. 3 is a diagram of a web page displayed in a view of a browser that is used for selecting personal media while being placed on hold by a contact center.

FIG. 4 is a flow diagram of a process for playing personal media while being placed on hold by a contact center.

FIG. 5 is a flow diagram of a process for playing personal media while being placed on hold by a contact center.

FIG. 6 depicts a second system in accordance with embodiments of the present disclosure.

FIG. 7 depicts a third system in accordance with embodiments of the present disclosure.

FIG. 8 depicts a second flow diagram of a process for playing personal media while being placed on hold in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a first illustrative system 100 for playing personal media while a user is placed on hold by a contact center 120. The first illustrative system 100 comprises communication endpoints 101A-101N, a network 110, a contact center 120, agent terminals 130A-130N, radio/television stream(s) 140, and audio/video stream(s)/file(s) 141.

The communication endpoints 101A-101N can be or may include any communication endpoint device that can communicate on the network 110, such as a Personal Computer (PC), a telephone, a video system, a cellular telephone, a Personal Digital Assistant (PDA), a tablet device, a notebook device, a laptop, a smartphone, and/or the like. The communication endpoints 101A-101N are user devices where a communication sessions ends. The communication endpoints 101A-101N are not network elements that facilitate and/or relay a communication session in the network, such as a communication manager or router. As shown in FIG. 1, any number of communication endpoints 101A-101N may be connected to the network 110.

The communication endpoint 101A further comprises a contact center application 102A, a display 103A, media file(s) 104A, a browser 105A, and a local media player 106A. The contact center application 102A can be or may include any software application that can be loaded on the communication endpoint 101A that can provide services for the contact center 120. For example, the contact center application 102A may provide a user interface that allows a user to initiate a voice call, initiate a video call, send an email, send a text message, initiate a virtual reality session, initiate an IM session, and/or the like to the contact center. The contact center application 102A may be used for digital self-service in addition to assisted service via a contact center. For example, the contact center application 102A may be a self-service banking application that includes the ability to place voice/video calls via WebRTC to a contact center 120.

The display 103A can be or may include any hardware display that can present information to the user, such as a touch screen, a Light Emitting Diode (LED) display, a plasma display, a Cathode Ray Tube (CRT), a liquid crystal display, and/or the like.

The media files 104A are any media files 104A that are stored locally on the communication endpoint 101A. The media files 104A may be music files, video files, audio files, movies, and/or the like.

The browser 105A can be or may be any known browser, such as Google Chrome®, Mozilla Firefox®, Internet Explorer®, Safari®, Opera®, and/or the like. The browser 105A can communicate with the contact center 120 by uploading a webpage provided by the web server 125.

The local media player 106 can be any media player that is installed on the communication endpoint 101A, such as iTunes®, Windows Media Player®, VLC media player, Kodi, GOM Player, and/or the like. The local media player 106 may be a media player that is embedded into the browser 105 that uses JavaScript to play the media file(s) 104, radio/television stream(s) 140, audio/video stream(s)/file(s) 141, and/or the like.

In one embodiment, the communication endpoint 101A may comprise a subset of the elements 102A-106A. For example, the communication endpoint 101A may not have the contact center application 102A. In this embodiment, the communication endpoint 101A may access the contact center 120 via the browser 105A/web server 125. For instance, the user, via the browser 105 (e.g., as discussed later in FIG. 3), may select a media file 104 that is played by a local media player 106 embedded in the browser 105. Alternatively, the communication endpoint 101A may communicate with the contact center 120 via the contact center application 102A instead of via the browser 105A/web server 125.

Although not shown for simplicity, the communication endpoints 101B-101N may also comprise one or more of the elements 102-106. For example, the communication endpoint 101B may comprise elements 102B-106B and the communication endpoint 101N may comprise elements 102N-106N.

The network 110 can be or may include any collection of communication equipment that can send and receive electronic communications, such as the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), a Voice over IP Network (VoIP), the Public Switched Telephone Network (PSTN), a packet switched network, a circuit switched network, a cellular network, a combination of these, and/or the like. The network 110 can use a variety of electronic protocols, such as Ethernet, Internet Protocol (IP), Session Initiation Protocol (SIP), Web Real-Time Communication (WebRTC) protocol, H.323, video protocols, Hyper Text Transport Protocol (HTTP), Integrated Services Digital Network (ISDN), and/or the like. Thus, the network 110 is an electronic communication network configured to carry messages via packets and/or circuit switched communications.

The contact center 120 can be or may include any hardware coupled with software that can route and manage communications in the contact center 120, such as a Private Branch Exchange (PBX), a communication manager 121, a session manager, a call center, and/or the like. The contact center 120 further comprises the communication manager 121, IVR system(s) 122, contact center queue(s) 123, media file(s) 124, and a web server 125.

The communication manager 121 can be or may include any hardware coupled with software that can route and manage communications in the contact center 120, such as a PBX, a session manager, a switch, a router, and/or the like. The communication manager 121 can manage various types of communications in the contact center 120, such as voice communications, video communications, emails, Instant Messaging (IM) communications, text messaging, virtual reality communications, and/or the like.

The IVR system(s) 122 can be or may include any hardware coupled with software that can provide an automated voice interaction with a caller. The IVR system(s) 122 typically provides a series of menus that can be used by the caller to get service from the contact center 120. The IVR system(s) 122 may provide other features, such as music-on-hold when the caller is placed on hold in one of the contact center queues 123. In one embodiment, the IVR system 122 may be a video/virtual reality IVR system 122 that provides one or more visual avatars that provides navigation by asking the caller questions. For example, an avatar provided by the IVR system 122 may ask the caller for a specific product that the caller is calling about.

The contact center queue(s) 123 are designed to hold incoming calls while the caller is waiting to be connected to a contact center agent (e.g., a contact center agent at agent terminal 130A). The contact center queue(s) 123 may hold any number of incoming calls. The contact center queue(s) 123 may have various wait times for a call that is on hold based on a current call volume in the contact center 120. The contact center queue(s) 123 may support one or more types of communications, such as, voice calls, video calls, emails, Instant Message sessions, text messages, virtual reality communications, and/or the like. As discussed herein and in the claims, the use of the term “on hold” or “hold” also includes where a communication (e.g., a voice or video call) is placed into a contact center queue 123.

The media files 124 can be or may include any media files that can be streamed from the contact center 120 while a user is in hold, such as music files, audio files, advertisements, announcements, video files, movies, radio streams, television streams, and/or the like. The media files are non-personalized media files that are streamed to contact center callers.

The web server 125 can be or may include any web server that can provide one or more web pages to the browser 105, such as Apache®, Nginx®, Internet Information Server®, LiteSpeed Web Server®, and/or the like. The web server 125 may provide multiple webpages. In one embodiment, the web server 125 may provide a variety of webpages, such as help webpages, contact webpages, product webpages, and/or the like.

The agent terminals 130A-130N can be or may include any communication device that is used by a contact center agent, such as, the communication endpoint 101. The agent terminals 130A-130N may comprise multiple agent terminals 130A-130N for each contact center agent. For example, a contact center agent may have a telephone and a personal computer.

The radio/television stream(s) 140 can be or may include any types of media streams that are streamed as part of a radio/television programming. The radio/television stream(s) 140 can be reached in various ways, such as based on a Uniform Resource Locator (URL), based on a network address, and/or the like.

The audio/video stream(s)/file(s) 141 can be or may include any files/media streams that can be accessed by the communication endpoint 101 via the network 110. The audio/video stream(s)/file(s) 141 may include media files that are accessible via web sites.

FIG. 2 is a diagram of a user interface 200 for selecting personal media while the user is placed on hold by the contact center 120. FIG. 2 is an exemplary diagram of a user interface that is provided by the contact center application 102. The user interface 200 comprises media selection radio button 201, listed local media 210A, listed radio stations 210B, listed television stations 210C, listed cloud media 210N, stream media button 220, and cancel button 221.

The listed local media 210A, in this example, shows two selections for local media: 1) the Beatles White Album, and 2) the Black Panther movie. The listed radio stations 210B comprises: 1) FM 99.0 KBCQ Rock 99 and 2) AM 1280 KRXR Talk Radio. The listed television stations 210C comprises: 1) KRXP Fox Local Channel 3 and 2) KXMP CBS Channel 5. The listed cloud media 210N comprises: 1) Bruno Mars—My Song, and 2) Pink—Please Don't Leave Me.

The user interface 200 is displayed in the display 103, by the contact center application 102A, when a user is placed on hold by the contact center 120. For example, the user may bring up the contact center application 102A on the communication endpoint 101A. The user may then select a button to initiate a voice call to the contact center 120. The voice call may be established using various protocols, such as SIP, H.323, video protocols, and/or the like. At some point the user is placed on hold by the contact center 120 and the contact center application 102 then displays the user interface 200.

If the user wants to play their own personalized media while on hold, the user selects the media selection radio button 201 (YES as displayed). The selection of “YES” on the media selection radio button 201 causes the different media selection options 210A-210N to be displayed along with the stream media button 220 and the cancel button 221. The user then selects one or more media options that the user wants to play, which then enables the stream media button 220. Depending upon the selected option, other media options may or may not be selectable. For example, as shown in FIG. 2, selection of a live media stream (e.g., FM 99.0 FBCQ Rock 99) may cause all the other selections to be disabled (not selectable). If the option is to play a media file 104 (or group of media files 104) the user may be able to select additional media files 104 to be played. For example, (although not shown) the user may be able to select the Beatles White Album and an additional media file 104 to play. The order that the media files 104 are played in may be based on the same order of selection by the user.

The user then selects the stream media button 220, which begins the play of the selected media source(s). For example, as shown in FIG. 2, if the user selected the stream media button 220, the FM 99.0 KBCQ Rock 99 radio stream would be played to the user while the user is waiting on hold. If the user does not want to play personalized media, the user selects the cancel button 221.

FIG. 3 is a diagram of a web page displayed in a view of a browser 300 that is used for selecting personal media while being placed on hold by a contact center 120. FIG. 3 shows an exemplary display 103 of a communication endpoint 101 where the browser 105 is displayed. The display 103 shows an exemplary view of the browser 300. The view of the browser 300 displays an option to play media while on hold 301, a yes button 302, and no button 303. FIG. 3 also shows a browse window 304.

The view of the browser 300 is displayed to a user based on the user navigating with the browser 105 to the web server 125 of the contact center 120. After the user has initiated a call (i.e., voice, video, or virtual reality), the view of the browser 300 is displayed to the user when the user is placed on hold by the contact center 120. The communication session between the browser 105 and the web server 125 may use various protocols, such as Hyper Text Markup Language (HTML), WebRTC, video protocols, and/or the like. For example, the user may enter a URL for the web server 125, which gives the user an option (not shown) to make a video call, via WebRTC with the contact center 120. After the user selects the option to make the video call, when the user is placed on hold by the contact center 120, the view of the browser 300 (without the browse window 304) is displayed to the user.

If the user does not want to play personalized media while placed on hold by the contact center 120, the user can select the no button 303. Otherwise, if the user wants to play personalized media while on hold, the user can select the yes button 302. This results in the browse window 304 being displayed to the user in step 310. By using the browse window 304, the user can select a media file 104 (e.g., a music or video file) to play while on hold. After the user selects the media file from the browse window 304, a media player in is executed in the web page and plays the selected media file.

In an alternative embodiment, instead of displaying the browse window 304 in step 310, when the user selects the yes button 302, a local media player 106 could be invoked by the browser 105 based on a protocol URL. A protocol URL is where an application (i.e., local media player 106) has registered with the operating system so that the application can be invoked from the browser 105. For example, Microsoft Windows® allows an application to modify the Windows Registry with the protocol URL (e.g., see http://msdn.microsoft.com/en-us/library/aa767914(VS.85).aspx). When a web page is loaded in the browser 105, the web page invokes the protocol URL and the local media player 106 (e.g., iTunes®) is executed. This allows the user to select the local media player 106 to play media while being placed on hold by the contact center 120. When the user is taken off hold, a similar process is used by the loaded webpage to un-invoke the local media player 106 to stop playing the user's personal media.

The user interface 200 and the view of the browser 300 are exemplary embodiments of where a user is placed on hold in a voice and/or video communication session. If the user is in a voice only communication session, the user may only be able to select audio files to stream. If the user is placed on hold in a video session, the user may see and select both audio and/or video files to stream. Alternatively, the user may be in a voice only communication session and can play a video file while in the voice only communication session.

In addition, the process of placing a user on hold may also work for a virtual reality call. For example, when the user is placed on hold in a virtual reality call, a virtual reality character may walk up to the user's virtual reality character and ask the user's virtual reality character if the user wants to play their personalized media while they are placed on hold by the contact center 120. The user's yes response could either bring up user interface 200 or browse window 304. Alternatively, a billboard may be displayed in the virtual reality environment to the user's virtual reality character where the user can touch the billboard (similar to user interface 200) to select personalized media to play.

In addition, when the user is placed on hold (assuming that the user streams an audio file), the user is placed in a virtual line with other users who are waiting to see a contact center agent who is in a virtual room. As the other users ahead of the user (i.e., users higher in the contact center queue 123) get serviced by the contact center agent (e.g., they walk into the room), the user moves up in the line. When the user is transferred to the contact center agent, the user walks into the room and discusses the issue virtually with the contact center agent in the virtual room. At this point, the user's personal media is stopped.

FIG. 4 is a flow diagram of a process for playing personal media while being placed on hold by the contact center 120. Illustratively, the communication endpoints 101A-101N, the contact center application 102A, the display 103A, the media file(s) 104A, the browser 105A, the local media player 106, the network 110, the contact center 120, the communication manager 121, the IVR system(s) 122, the contact center queue(s) 123, the media files(s) 124, the web server 125, the agent terminals 130A-130N, the radio/television stream(s)140, and the audio/video stream(s)/file(s) 141 used by stored-program-controlled entities, such as a computer or microprocessor, which performs the method of FIGS. 4-5 and the processes described herein by executing program instructions stored in a computer readable storage medium, such as a memory (i.e., a computer memory, a hard disk, and/or the like). Although the methods described in FIGS. 4-5 are shown in a specific order, one of skill in the art would recognize that the steps in FIGS. 4-5 may be implemented in different orders and/or be implemented in a multi-threaded environment. Moreover, various steps may be omitted or added based on implementation.

The process starts in step 400 where a communication session is established between the communication endpoint 101A and the contact center 120. The communication session between the communication endpoint 101A and the contact center 120 may be established via the contact center application 102A or via a webpage loaded in the browser 105 from the web server 125. The user is then placed on hold in step 402. For example, the user of the communication endpoint 101A may initiate a voice call to the contact center 120 (via the contact center application 102A or the browser 105A) and is initially connected with the IVR system 122. Via the IVR system 122, the user is placed on hold (e.g., by being placed into the contact center queue 123). In response to the user being placed on hold, the contact center 120 sends a message, in step 404, to the communication endpoint 101A (i.e., to the contact center application 102A or the webpage loaded in the browser 105) that indicates that the communication session has been placed on hold by the contact center 120.

As shown in FIG. 4, the message of step 404 is a message that is sent outside of a media stream (e.g., not a message where the IVR system 122 tells the user that he/she has been placed on hold). Moreover, in one embodiment, the message of step 404 is not a communication session control channel message (e.g., SIP or H.323) that actually causes the communication endpoint 101A to be placed on hold; instead, the message of step 404 simply notifies the communication endpoint 101A that the contact center placed the user on hold.

The contact center 120 may optionally start to stream media while the user is placed on hold in step 406. For example, the contact center 120 may stream the media file 124 (i.e., music-on-hold) to the communication endpoint 101A in the voice communication session. In response to receiving the message of step 404 that the communication session has been placed on hold, the contact center application 102A or the browser 105 displays an option for the user to play personalized media in step 408. For example, the user interface 200 or the view of the browser 300 is displayed to the user of the communication endpoint 101A in step 408. In order for the user interface 200 to be displayed, the contact center application 102A and/or the downloaded web page may search the communication endpoint 101A (if possible by the downloaded web page), the radio/television stream(s) 140, and/or the audio/video stream(s)/file(s) 141 for media files/media streams to display. This may be done based on an Application Programming Interface (API) call that checks for local media and media that is identified by a URL (network based media files/streams). The search may occur in response to the user indicating that the user wants to stream personal media (step 410) or prior to the user indicating that the user wants to stream personal media.

The user indicates, in step 410, that the user wants to play personalized media. For example, the user can indicate that the user wants to play personalized media by selecting the stream media button 220, by browsing to a media file in the browse window 304, or by selecting a media file from the local media player 106A when invoked by a protocol URL. The personal media is then played, in step 412, to the user of the communication endpoint 101A.

In addition, when the user indicates that the user wants to play personalized media in step 410, the contact center application 102A or the webpage loaded in the browser 105 sends, in step 414, a message that the user of the communication endpoint 101A would like to play personalized media while the communication session is placed on hold by the contact center 120. In response to receiving the message of step 414, the contact center 120 stops streaming, in step 416, the media stream of step 406 (if the media stream is being sent).

In one embodiment, the message of step 414 is not sent to the contact center 120. In this case, the contact center application 102A or the web page loaded in the browser 105 ignores the media stream that is sent in step 406.

At a later point in time, the contact center 120 determines, in step 418, that the user has been taken off hold. For example, the voice communication session may have been transferred from the contact center queue 123 to the agent terminal 130A (e.g., a telephone of a contact center agent). When the user has been taken off hold by the contact center 120 in step 418, the contact center 120 sends, in step 420, a message to the communication endpoint 101A to stop playing the personal media stream. In response to receiving the message of step 420, the communication endpoint 101A (i.e. the contact center application 102A/loaded webpage/local media player 106A) stops playing the personal media stream in step 422. The user is then connected to a contact center agent in step 424. In one embodiment, instead of connecting to a contact center agent in step 424, the user may be taken off hold and connected to an automated agent. For example, the user may be connected back to IVR system 122 to navigate one or more IVR menus.

FIG. 5 is a flow diagram of a process for playing personal media while being placed on hold by the contact center 120. The process starts in step 500 where a communication session is established between the communication endpoint 101A and the contact center 120. The communication session between the communication endpoint 101A and the contact center 120 may be established via the contact center application 102A or via a webpage loaded in the browser 105 from the web server 125. The user is then placed on hold in step 502. In response to the user being placed on hold (e.g., being placed into the contact center queue 123), the IVR system 122 asks the user if the user would like to play personal media in step 504. For example, the IVR system 122 may ask the user to select “1” if the user wants to play personal media or to select “2” if the user does not want to play personal media. If the user elects to not play personal media in step 506 (e.g. by selecting “2”), a media stream (e.g., music-on-hold from streaming media file 124) is sent by contact center 120, in step 506, to the communication endpoint 101A; the then process goes to step 522 where the user is connected to the contact center agent. When the user is connected to the contact center agent in step 522, the media stream being sent by the contact center 120 (step 508) ends.

If the user provides input to play personal media in step 506 (e.g., for example, the user selects “1” on the keypad of the communication endpoint 101A), the contact center 120 sends, in step 510, a message to the communication endpoint 101A (the contact center application 102A/web page loaded in the browser 105) that the user has selected to play personal media. In response to receiving the message of step 510, the contact center application 102A or the browser 105 displays an option for the user to play personalized media in step 512. For example, the user interface 200 or the view of the browser 300 is displayed to the user of the communication endpoint 101A in step 512.

In order for the user interface 200 to be displayed in step 512, the contact center application 102A or loaded web page may search the communication endpoint 101A (if possible by the loaded web page), the radio/television stream(s) 140, and/or the audio/video stream(s)/file(s) 141 for media files/media streams to display. This may be done based on an Application Programming Interface (API) call that checks for local media and media that is identified by a URL (network based media files/streams). The search may occur in response to the user indicating that the user wants to stream personal media (step 514) or prior to the user indicating that the user wants to stream personal media.

The user indicates, in step 514, that the user wants to play personalized media. For example, the user can indicate that the user wants to play personalized media by selecting the stream media button 220, by browsing to a media file in the browse window 304, or by selecting a media file from local media player 106A when invoked by a protocol URL. In response to the user indicating that the user wants to play personalized media in step 514, the personal media is played to the user in step 516.

At a later point in time, the contact center 120 determines, in step 518, that the user has been taken off hold. For example, the voice communication session may have been transferred from the contact center queue 123 to the agent terminal 130A (e.g., a telephone of a contact center agent). When the user has been taken of hold by the contact center 120, the contact center 120 sends, in step 520, a message to the contact center application 102A or the loaded webpage to stop playing the personal media stream. In response to receiving the message of step 520, the communication endpoint 101A (i.e. the contact center application 102A/loaded webpage/local media player 106A) stops playing the personal media stream in step 522. The user is then connected to a contact center agent in step 524. In one embodiment, instead of connecting to a contact center agent in step 524, the user may be taken off hold and connected to an automated agent. For example, the user may be connected back to IVR system 122 to navigate IVR menus.

FIGS. 1-5 discuss embodiments where a contact center application 102 is used or where the web server 125 provides a web page that is displayed via the browser 105. In one embodiment, the contact center application 102/web page that is displayed via the browser 105 may include WebRTC capabilities. For example, the WebRTC application may be a self-service banking application. The self-service banking application has two primary modes of operation: 1) a self-service function (non-real-time), and 2) a call placement function (real-time). The self-service function allows the user access non-real time digital services, such as, to check bank balances, make deposits, and/or the like. The self-service function uses a separate communication path with the contact center 120.

The call placement function allows the user to make a real-time call to the contact center 120 to talk to a contact center agent. The call placement function can work in different ways. For example, the contact center 120 can tell a server-side web/mobile infrastructure (not shown) that a call has been placed on hold and answered (taken off hold). The server-side web/mobile infrastructure would then relay this state information to the browser 105/contact center application 102. Alternatively, the contact center 120 can notify a WebRTC library/client (in the contact center application 102 or browser 105) that a call has been queued/held and answered/un-held. The WebRTC library/client would then notify the digital self-service part of the browser 105/contact center application 102.

Although the processes described herein are described where a contact center 120 places a user on hold, the process will also work for any system that places a user on hold. For example, instead of a contact center placing user on hold, a PBX or other communication endpoint 101 may send the same messages as the contact center 120.

Today, it is common for customers to use more of a web centric approach to communicate with a contact centers, such as by using an application installed on a smart phone, tablet, or smart PC to make and receive calls. Some of these applications utilize WebRTC as a protocol for communication with a destination server or other endpoint. For example, a customer places a call through a smart phone application (or, more simply, an “app”) and is connected to a contact center of a bank. As mentioned on the WebRTC website (https://webrtc.org, which is herein incorporated by reference), there are JavaScript APIs for all major web browsers, while the same functionality is available through libraries for native mobile apps running on Android, IOS and other mobile platforms.

It should be appreciated that modifications to the network topology may be made, such as when both endpoints are within the same local network and able to directly connect in a peer-to-peer configuration. Accordingly, in such embodiments, the use of a WebRTC server may be omitted. However, generally, and in the embodiments herein, a WebRTC server, such as a server implementing Traversal Using Relay NAT (TURN) is utilized for relaying network traffic.

In one embodiment, a customer who is enqueued to speak to an agent is placed on hold and presented with the opportunity to have personalized wait treatment, such as to be presented with media content (e.g., audio, video, multi-media, live audio/video, etc.) from their own device or from other sources unrelated to the contact center or other communication equipment utilized to communicate with the contact center or agent of the contact center. More specifically, a call placed to a contact center utilizing voice over internet protocol (VoIP) may be augmented with the personalized wait treatment. An endpoint, such as one of communication endpoints 101, may be configured with an application that maintains the connection to the contact center while on hold and plays media content from another source during the hold. When an agent becomes available, the application discontinues playing the media content and connects the communication to the agent.

FIG. 6 depicts system 600 in accordance with embodiments of the present disclosure. In one embodiment, a customer uses one of communication endpoints 101, such as communication endpoint 101B embodied as an app executed by a microprocessor of a smart phone, and then clicks on “Call” button to talk to customer representative or agent, utilizing one of agent terminals 130, via contact center 120.

In another embodiment, system 600 illustrates system 100 (see FIG. 1) comprising an alternative configuration wherein contact center 120 comprises or utilizes WebRTC server 602, PBX 604, and automatic call distribution 606 to receive, enqueue, and connect communication endpoint 101B to a designated agent terminal, such as agent terminal 130A. In another embodiment, one or more of WebRTC server 602, PBX 604, and/or automatic call distribution 606 are configured to embodied in, or to comprise, one or more of communication manager 121, IVR system(s) 122, contact center queue(s) 123, and/or web server 125. A communication path may include WebRTC Server 602, automatic call distribution 606, and one or more agent terminals 130.

When automatic call distribution, or other component, answers the call from communication endpoint 101B, the call may receive initial processing, such as with IVR system(s) 122 or other component, such as may be utilized to gather initial information (e.g., particular area or reason for the call, extension of an agent, customer identification information, etc.). No agent, or no relevant or qualified agent, may be currently available to take the call which is then placed on hold and enqueued until such time as an appropriate agent becomes available.

The application executed by communication endpoint 101B receives a notification, such as a SIP message (e.g., “INFO”) or a non-SIP notification (see FIG. 4, step 404) and, in response, the application may present a menu of media options (see FIG. 2). However, while a web browser may be configured by a server to present content, including media content from a third-party provider (i.e., a party requiring, at least, a discrete communication session from the communication session utilized to communicate with contact center 120), a web application executing on communication endpoint 101B connects to other sources for media content, and performs the management of the connections, in part, from the signals received from WebRTC Server 602. The connections may require a setup and take-down on a SIP signaling path or, in another embodiment, access a link to a media source wherein the media source is local to communication endpoint 101B or remote, such as server streaming music, on-line radio or television station, or other media content.

FIG. 7 depicts system 700 in accordance with embodiments of the present disclosure. In one embodiment, communication endpoint 101B placed a call for an agent, associated with a selected one of agent terminals 130. The call may be a VoIP call for communication endpoint 101B but a public switched telephone network (PSTN) call for contact center 120. Accordingly, a translation may be required to enable communication and message signaling between VoIP and PSTN networks. Other components may be utilized, such as a gateway, which are omitted to avoid unnecessarily complicating the figures and description.

In one embodiment, SIP Trunks 702 converts the VoIP portion of the call into a PSTN portion and vice versa. When the call originates, SIP trunks 702 allocate connection resources and routs a circuit switched call to PBX 604. PBX 604 may process the call normally (e.g., perform any initial information gathering, enqueuing, placing the call on hold, taking the call off hold, and connecting to a selected agent terminal 130). When placing a call on hold contact center 120 may originate a notification (e.g., a message comprising spoken sequence of words, DTMF or other tones or encoded signal) provided, via PBX 604 to SIP trunk 702. The notification is then received and processed by an application on communication endpoint 101B. The application then connects communication endpoint 101B to a previously determined source of media content and presents the media content on communication endpoint 101B. Communication endpoint 101B may continue to monitor the connection with contact center 120.

When contact center 120 takes the call off hold, the application terminates the connection to the media content or pauses the media content and connects the call to the agent associated with the selected agent terminal 130.

FIG. 8 depicts flow diagram 800 in accordance with embodiments of the present disclosure. In one embodiment, a customer utilizes a particular endpoint communication device 101, such as communication endpoint 101B, to place a call to contact center 120 in step 802. In step 804, contact center 120 performs any preliminary information gathering, such as via IVR system(s) 122, and places the call on hold. In step 806 communication endpoint 101B is notified that the call has been placed on hold.

Step 806 may originate from a VoIP system or WebRTC system, such as WebRTC server 602 (see, FIG. 6) and comprise a SIP message, such as “INFO” and, in response, communication endpoint 101B acknowledges with “200 OK”. In another embodiment, step 806 may originate from a source, such as a PSTN or PBX 604 (see FIG. 7). Accordingly, step 806 may comprise audio content to signal to communication endpoint 101B that the call is on hold. For example, step 806 may comprise a set of standard tones (e.g., DTMF) or non-standard tones. For example, an application utilized to place the call by communication endpoint 101B may be known to contact center 120 to initiate an on-hold state when the sound received (step 806) comprises a one second tone of 1633 Hz and optionally omits presenting such a frequency to the user via an output component, such as a speaker of communication endpoint 101B. It should be appreciated that any tone, tones, or sequence of tones may be established between communication endpoint 101B and contact center 120 to signal an on-hold state in step 806.

In another embodiment, speech recognition service operating on communication endpoint 101B may hear spoken (e.g., live generated or automated voice) presented by contact center 120 stating that the call is on hold (e.g., “Please wait for the next representative,” “Please hold,” “Your call is important to us.” etc.). Upon detecting such content in the audio, or being directly signaled via a SIP message, step 808 causes communication endpoint to process the on-hold state of the call.

Step 808 may present a user interface, similar to user interface 200, by the application executing on communication endpoint 101B. Communication endpoint 101B, as directed by a processor executing the application utilized for placing the call in step 802, may present options, such as to play a local media file or, in another embodiment, connect to a remote source to obtain media content (e.g., internet radio stream(s) 140, audio/video stream(s)/files(s) 141, or other streaming music service, on-line news and sports content, etc.). Optionally, step 808 may also automatically mute a microphone of communication endpoint 101B. A connection may then be established in step 810 with media source 801.

Step 810 may directly connect to media source 801, such as to play a local media file or call a secondary application, such as via an API or other programming interface, to perform step 810. For example, step 810 may comprise calling a media player configured to play remote media content from media source 801, such as radio/television stream(s) 140, audio/video stream(s)/file(s) 141. Step 810 may establish a media session, such as by accessing a local file for playback by a playback application, or when remote, perform any authentication and selection as may be required by media source 801. As a result, media session is established and streamed in step 812 while the call is on hold and as established via communication endpoint 101B. In a further embodiment, step 812 may pause the communication session initiated in step 802 in order to save bandwidth. This may terminate media content being sent between communication endpoint 101B and contact center 120, however, if a “heartbeat” signal is utilized in order to notify one of communication endpoint 101B and contact center 120 that the other is still connected during an idle (on hold) media session, such “heartbeat” messages may continue.

Step 814 is a counterpart to step 806 to signal to the application utilized to place the call in step 802 that the call is now off hold. Accordingly, step 806 may comprise a SIP message, such as “INFO” or a tone(s), to which communication endpoint 101B may respond (e.g., 200 OK″). In another embodiment, sound is conveyed in step 814, such as when contact center 120 is a PSTN utilizing a SIP Trunk(s) (e.g., SIP Trunks 702), as an intermediary to translate to communication endpoint 101B utilizing VoIP.

Step 814 may comprise a particular tone, tones, sequence of tones, or spoken content. The spoken content may be previously agreed upon between communication endpoint 101B and contact center 120 (e.g., “Thank you for holding. You're call will now be connected to an agent.”) or a speech recognition system may determine that the sound comprises speech associated with being off-hold (e.g., “Thank you for waiting, my name is . . . ”, “Thanks for calling . . . ”, “Hello . . . ”, etc.). Step 816 processes the off-hold state, such by unmuting the microphone if muted in step 808. Step 816 may signal any secondary applications (e.g., music player application) utilized in step 810 and 812 to terminate media streamed in step 812. Accordingly, in step 818 the media session is terminated or optionally maintained with the media streaming paused.

Step 820 resumes the communication session established in step 802 with contact center 120 and with a selected agent utilizing an associated agent terminal 130. At this point, the agent and customer may discuss the reason for the call and its resolution or additional steps to perform and, once concluded, step 824 terminates the session. This may be a SIP “BYE” followed by a “200 OK” or, when contact center 120 is a PSTN system, going “on hook.”

Optionally, in response to ending the call, communication endpoint 101B may present in step 826 an option, or automatically and without human intervention, to cause the media stream, if paused in step 818, to be resumed. If the media stream was terminated in step 818, then in another embodiment, step 826 may provide an option to have communication endpoint 101B reestablish the media stream and/or other browsing such as through use of a browser application of contact center 120 or other application executing on communication endpoint 101B.

In another embodiment, step 814 may be sent as a precursor announcement in anticipation of the call being taken off hold. For example, contact center 120 may determine that the call with communication endpoint 101B has, or soon will, advance to the front of the queue and an agent will become available to talk with the customer within a previously determined, and relatively short period of time, such as 5 to 30 seconds. As discussed above, this may be a particular tone, tones, tone sequence, or spoken content (e.g., “You will be connected to an agent within the next ten seconds.” “We will now connect you to an agent.” etc.). As a result, steps 816-828 may proceed as described above. Alternatively, step 818 may perform a sequence of operations, such as to gradually bring the customer's focus back to the communication initiated in step 802. For example, if the media session initiated in step 812 comprises video, communication endpoint 101B may overlay the video image presented by an output component (e.g., video display) with text or a countdown timer as to when the call will be taken off hold. If the media session comprises audio or is audio-only, the volume may be decreased and/or a message inserted into the audio (e.g., “You are about to be connected to an agent.”). A pop-up may also be incorporated for display on a screen of communication endpoint 101B. Additionally or alternatively, step 816 may prompt the customer as to whether they wish the media stream to be terminated or paused, such as to be resumable in step 828.

In another embodiment, a second communication device or devices (not shown) may be engaged in a peer-to-peer communication with communication endpoint 101B. The second communication device may provide the messages and communication services of contact center 120 but limited to a single user of the second communication device. Accordingly, the steps of process 800 performed by contact center 120 may be performed by a second communication device configured with a microprocessor with machine executable instructions for performing executing instructions to perform the such steps, comprising establishing a communication session with communication endpoint 101B (step 802), provide an on-hold message (step 806), provide an off-hold message (step 814), resume the communication session (step 820), and when concluded, terminate the communication session (step 824). Accordingly, the second communication endpoint may comprise another embodiment of one of communication endpoints 101 when configured to perform the steps described herein and enable communication endpoint 101B to receive (step 806) and process (step 808) an on-hold message, establish a second media stream (810) while on hold, receive (step 814) and process (816) an off-hold message and, in response, terminate/pause the second media stream (step 818), and resume the communication session (step 820) until concluded and terminated (step 824).

Examples of the processors as described herein may include, but are not limited to, at least one of Qualcomm® Snapdragon® 800 and 801, Qualcomm® Snapdragon® 610 and 615 with 4G LTE Integration and 64-bit computing, Apple® A7 processor with 64-bit architecture, Apple® M7 motion coprocessors, Samsung® Exynos® series, the Intel® Core™ family of processors, the Intel® Xeon® family of processors, the Intel® Atom™ family of processors, the Intel Itanium® family of processors, Intel® Core® i5-4670K and i7-4770K 22 nm Haswell, Intel® Core® i5-3570K 22 nm Ivy Bridge, the AMD® FX™ family of processors, AMD® FX-4300, FX-6300, and FX-8350 32 nm Vishera, AMD® Kaveri processors, Texas Instruments® Jacinto C6000™ automotive infotainment processors, Texas Instruments® OMAP™ automotive-grade mobile processors, ARM® Cortex™-M processors, ARM® Cortex-A and ARM926EJ-S™ processors, other industry-equivalent processors, and may perform computational functions using any known or future-developed standard, instruction set, libraries, and/or architecture.

Any of the steps, functions, and operations discussed herein can be performed continuously and automatically.

However, to avoid unnecessarily obscuring the present disclosure, the preceding description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scope of the claimed disclosure. Specific details are set forth to provide an understanding of the present disclosure. It should however be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein.

Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switch network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system. For example, the various components can be located in a switch such as a PBX and media server, gateway, in one or more communications devices, at one or more users' premises, or some combination thereof. Similarly, one or more functional portions of the system could be distributed between a telecommunications device(s) and an associated computing device.

Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosure.

A number of variations and modifications of the disclosure can be used. It would be possible to provide for some features of the disclosure without providing others.

In yet another embodiment, the systems and methods of this disclosure can be implemented in conjunction with a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device or gate array such as PLD, PLA, FPGA, PAL, special purpose computer, any comparable means, or the like. In general, any device(s) or means capable of implementing the methodology illustrated herein can be used to implement the various aspects of this disclosure. Exemplary hardware that can be used for the present disclosure includes computers, handheld devices, telephones (e.g., cellular, Internet enabled, digital, analog, hybrids, and others), and other hardware known in the art. Some of these devices include processors (e.g., a single or multiple microprocessors), memory, nonvolatile storage, input devices, and output devices. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.

In yet another embodiment, the disclosed methods may be readily implemented in conjunction with software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this disclosure is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized.

In yet another embodiment, the disclosed methods may be partially implemented in software that can be stored on a storage medium, executed on programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this disclosure can be implemented as program embedded on personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated measurement system, system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system.

Although the present disclosure describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Other similar standards and protocols not mentioned herein are in existence and are considered to be included in the present disclosure. Moreover, the standards and protocols mentioned herein, and other similar standards and protocols not mentioned herein are periodically superseded by faster or more effective equivalents having essentially the same functions. Such replacement standards and protocols having the same functions are considered equivalents included in the present disclosure.

The present disclosure, in various embodiments, configurations, and aspects, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the systems and methods disclosed herein after understanding the present disclosure. The present disclosure, in various embodiments, configurations, and aspects, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments, configurations, or aspects hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and\or reducing cost of implementation.

The foregoing discussion of the disclosure has been presented for purposes of illustration and description. The foregoing is not intended to limit the disclosure to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the disclosure are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects of the disclosure may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention that the claimed disclosure requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the disclosure.

Moreover, though the description of the disclosure has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the disclosure, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter. 

What is claimed is:
 1. A communication component, comprising: a microprocessor; and a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that program the microprocessor to: establish a first communication session with a communication endpoint, wherein the communication endpoint comprises an application in communication with the communication component; send a first notification within the first communication session via the communication component to the communication endpoint wherein the first notification notifies the communication endpoint that the first communication session is on hold to cause the communication endpoint to initiate a second communication session with a media source; and place the first communication session with the communication endpoint on hold.
 2. The communication component of claim 1, wherein the executable instructions further program the microprocessor to: send a second notification within the first communication session via the communication component to the communication endpoint, wherein the second notification notifies the communication endpoint that the first communication session is off hold to cause the communication endpoint to terminate the second communication session with the media source; and take the first communication session with the communication endpoint off hold.
 3. The communication component of claim 2, wherein the microprocessor takes the first communication session off hold after a delay, wherein the delay is determined in accordance with the communication endpoint processing the second notification in anticipation of the first communication session being taken off hold.
 4. The communication component of claim 1, wherein the first notification sent within the first communication session comprises a Session Initiation Protocol (SIP) signaling stream and a real-time media stream and wherein the first notification is sent as a SIP notification within the signaling stream.
 5. The communication component of claim 1, wherein the first notification sent within the first communication session comprises an audio signal encoded with content wherein the content indicates the communication session is on hold.
 6. The communication component of claim 1, wherein the communication component comprises a second communication endpoint.
 7. The communication component of claim 1, wherein the communication component comprises a server managing connections to a plurality of secondary communication endpoints, and wherein a selected one secondary communication endpoint of the plurality of secondary communication endpoints, is connected to the communication endpoint when the first communication session is taken off hold.
 8. A communication endpoint, comprising: a microprocessor; and a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that program the microprocessor to: establish a first communication session with a communication component; receive a first notification within the first communication session from the communication component, wherein the first notification notifies the communication endpoint that the first communication session is on hold; and in response to receiving the first notification, initiate a second communication session with a media source; and present media content from the media source by an output component of the communication endpoint.
 9. The communication endpoint of claim 8, wherein the executable instructions further program the microprocessor to: upon receiving the first notification, receiving an input selecting the media source from a plurality of media sources; and in response to receiving the input, initiating the second communication session with the selected media source of the plurality of media sources.
 10. The communication endpoint of claim 8, wherein the executable instructions further program the microprocessor to receive a second notification within the first communication session, wherein the second notification notifies the communication endpoint that the first communication session is off hold to cause the communication endpoint to terminate the second communication session with the media source.
 11. The communication endpoint of claim 10, wherein the microprocessor, upon receiving the second notification, performs an intermediary action comprising at least one of decrementing the volume of an audio portion of the second communication session, providing a pop-up notification, inserting a visual notification into a video portion of the second communication session, inserting an audible notification into the audio portion of the second communication session.
 12. The communication endpoint of claim 11, wherein the second notification is received within the first communication session upon the microprocessor determining the first communication session comprises an audio signal indicating the communication session is off hold.
 13. The communication endpoint of claim 10, wherein the microprocessor, wherein the second notification comprises a precursor announcement.
 14. The communication endpoint of claim 8, wherein the first notification is received within the first communication session comprising a Session Initiation Protocol (SIP) signaling stream and a real-time media stream, wherein the first notification is received as a SIP notification within the signaling stream.
 15. The communication endpoint of claim 8, wherein the first notification is received within the first communication session upon the microprocessor determining the first communication session comprises an audio signal indicating the communication session is on hold.
 16. The communication endpoint of claim 15, wherein the microprocessor, receives the audio signal indicating the communication session is on hold, wherein the audio signal comprises speech announcing the communication session is on hold.
 17. The communication endpoint of claim 8, wherein the microprocessor, upon receiving the first notification, mutes a microphone of the communication endpoint.
 18. A method, comprising: establishing a first communication session between a communication component and a communication endpoint over a network, wherein the communication endpoint comprises a microprocessor executing an application in communication with the communication component; sending a first notification within the first communication session from the communication component to the communication endpoint, wherein the first notification notifies the communication endpoint that the first communication session is on hold; initiating, by the communication endpoint in response to receiving the first notification, a second communication session with a media source; placing the first communication session with the communication endpoint on hold by the communication component; and presenting media content from the media source by an output component of the communication endpoint.
 19. The method of claim 18, further comprising: sending, by the communication component after the first communication session has been placed on hold, a second notification within the first communication session to the communication endpoint, wherein the second notification notifies the communication endpoint that the first communication session is off hold; terminating, by the communication endpoint, the second communication session with the media source in response to receiving the second notification; and taking the first communication session with the communication endpoint off hold by the communication component.
 20. The method of claim 18, further comprising: prompting an input to the communication endpoint selecting a media source from a plurality of media sources; and in response to receiving the input, initiating the second communication session with the selected media source of the plurality of media sources. 